Systems and methods of presenting simulated credit score information

ABSTRACT

In an embodiment, a computer system receives credit information relating to a consumer, and calculates a credit score associated with the consumer. The system constructs a credit score scenario user interface. The system maintains a plurality of credit score simulation scenarios, and calculates a plurality of simulated credit scores associated with respective credit score simulation scenarios. The system also constructs a credit score simulation control interface. The system maintains a plurality of credit score simulation parameters, and generates a user interface with a graphical indication of the calculated credit score and a plurality of sliders, each slider being divided into segments that are colored to graphically indicate the likely effect of repositioning the slider within the respective segment. When the user repositions the sliders, the graphical indication of the calculated credit score is adjusted, based on a recalculation of the credit score.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. application Ser. No.15/429,592, filed Feb. 10, 2017, titled “Systems and Methods ofPresenting Simulated Credit Score Information,” which is a continuationof U.S. application Ser. No. 13/326,803, filed Dec. 15, 2011, titled“Systems and Methods of Presenting Simulated Credit Score Information,”the entire contents of each are hereby incorporated by reference hereinand made part of this specification for all that they disclose. Thisapplication is related to, but does not claim priority from, U.S. patentapplication Ser. No. 10/452,155, filed May 30, 2003, now U.S. Pat. No.7,610,229; U.S. patent application Ser. No. 12/606,060, filed Oct. 26,2009, now U.S. Pat. No. 8,015,107; U.S. patent application Ser. No.11/150,480, filed Jun. 10, 2005, now U.S. Pat. No. 7,593,891; U.S.patent application Ser. No. 12/563,779, filed Sep. 21, 2009, now U.S.Pat. No. 7,925,582; and U.S. Prov. Pat. App. No. 60/384,650, filed May30, 2002. The disclosures of the above-listed applications are allhereby incorporated by reference as if set forth herein in theirentireties.

BACKGROUND

This disclosure relates to the field of consumer credit information andparticularly to the presentation of simulated credit score information.

The credit score is an important indicator of a consumer's financialhealth. Consequently, having a high credit score is important toconsumers for many reasons. A high credit score is required for suchthings as loan applications, rental applications, real estate mortgages,and so on. Thus, many consumers have a substantial interest in findingways to improve their credit scores.

There is much information available to consumers as to how to improvecredit scores. For example, sources provide advice to consumers to payoff loans, to establish certain numbers of credit accounts, to establishnew loans, to raise or lower credit card limits, and so on. However,this advice is generic to all consumers and does not provide informationspecific to a particular consumer's situation. The question for manyconsumers then is which of the suggested actions would be the mosteffective in improving that consumer's credit score based on thatconsumer's situation.

SUMMARY

Thus, it would be advantageous for consumers to be able to quicklyinvestigate the various actions that may be taken to change one's creditscore and the effect that those actions would have. In particular, itwould be advantageous for consumers to be able to visualize thoseeffects in an interactive and real time manner.

An embodiment is a computer-readable medium that operates a computersystem. The system receives credit information relating to a consumer.The system calculates a credit score associated with the consumer basedon the received credit information and further based on a credit scorecalculation algorithm. The system constructs a credit score scenariouser interface. The system maintains a plurality of credit scoresimulation scenarios and calculates a plurality of simulated creditscores associated with respective credit score simulation scenarios.Each simulated credit score is calculated based on the credit scorecalculation algorithm and further based on the received creditinformation with modifications in accordance with the respective creditscore simulation scenario. The system transmits first user interfacedata configured to cause the display of a user interface including alisting of information associated with respective credit scoresimulation scenarios, in conjunction with the simulated credit scoresfor respective credit score simulation scenarios. The system alsoconstructs a credit score simulation control interface. The systemmaintains a plurality of credit score simulation parameters andtransmits second user interface data configured to cause the display ofa user interface comprising a graphical indication of the calculatedcredit score. The second user interface data further comprises aplurality of sliders, each slider being associated with a credit scoresimulation parameter, each slider being divided into a plurality ofsegments that are colored to graphically indicate the likely effect ofrepositioning the slider within the respective segment. The system alsotransmits executable code in association with the second user interfacedata, The executable code is configured to update in real time, inresponse to the user repositioning one or more of the sliders, thegraphical indication of the calculated credit score, based on arecalculation of the credit score using at least parameters determinedfrom the one or more repositioned sliders.

In an embodiment, constructing the credit score scenario user interfacefurther comprises selecting a subset of the plurality of simulatedcredit score simulation scenarios, and wherein the listing ofinformation associated with respective credit score simulation scenariosis based on the selected subset of the plurality of simulated creditscore simulation scenarios.

In an embodiment, the first user interface data is further configured todisplay extended information for one or more of the respective creditscore simulation scenarios in response to a user interaction with thelisting of information.

In an embodiment, the first user interface data is further configured todisplay additional credit score simulation scenarios in response to auser interaction with the listing of information.

In an embodiment, the second user interface data is further configuredto display a graphical indication of a current credit score, and whereinthe executable code is configured to update the graphical indication ofthe calculated credit score but not to update the graphical indicationof the current credit score.

In an embodiment, each slider of the plurality of sliders is initiallypositioned based upon the credit information relating to the consumer.

In an embodiment, a system performs a method of automaticallycalculating credit score simulation information to a user. The systemreceives credit information relating to a consumer. The systemidentifies a plurality of credit score simulation scenarios, each creditscore simulation scenario including data indicating credit scoresimulation parameters associated with the respective credit scoresimulation scenario. The system executes, using a computer processor, acredit score simulation calculation for each of the credit scoresimulation scenarios. Each execution of the credit score simulationcalculation for a credit score simulation scenario is based on thecredit information and the credit score simulation parameters associatedwith the respective credit score simulation scenario. The executionproduces simulated credit scores for respective credit score simulationscenarios. The system constructs user interface data configured to causethe display of a user interface including a listing of informationassociated with respective credit score simulation scenarios, inconjunction with the simulated credit scores for respective credit scoresimulation scenarios. The system then transmits the constructed userinterface data.

In an embodiment, the method also includes calculating a credit scorebased on the credit information, and wherein the user interface furtherincludes the calculated credit score.

In an embodiment, at least one of the simulated credit scores aregreater than the calculated credit score, and at least some of thesimulated credit scores are less than the calculated credit score, andwherein the user interface graphically differentiates the greater andless simulated credit scores.

In an embodiment, the user interface is configured to display, uponclicking an element of the listing of information associated with aparticular credit score simulation scenario, expanded informationincluding further credit score simulation data related to the particularcredit score simulation scenario.

In an embodiment, the user interface is configured to display expandedinformation by requesting and receiving further credit score simulationdata from an external server.

In an embodiment, identifying the plurality of credit score simulationscenarios comprises selecting a subset of credit score simulationscenarios based at least in part upon the received credit information.

In an embodiment, the selected subset of credit score simulationscenarios is further based upon stored user preferences.

In an embodiment, the listing of information is sorted by the simulatedcredit scores for respective credit score simulation scenarios.

In an embodiment, a system performs a method of constructing a creditscore simulation control interface. The system receives creditinformation associated with a consumer. The system calculates, using acomputer processor, a credit score based on the received creditinformation. The system constructs user interface data configured tocause the display of a user interface comprising a graphical indicationof the calculated credit score. The user interface data furthercomprises a plurality of sliders, each slider being associated with acredit score simulation parameter, each slider being divided into aplurality of segments that are colored to graphically indicate thelikely effect of repositioning the slider within the respective segment.The system transmits the constructed user interface data. The systemtransmits executable code in association with the constructed userinterface data. The executable code is configured to update in realtime, in response to the user repositioning one or more of the sliders,the graphical indication of the calculated credit score, based on arecalculation of the credit score using at least parameters determinedfrom the one or more repositioned sliders.

In an embodiment, the graphical indication of the calculated creditscore comprises a colored dial and a pointer. The colored dial isdivided into a plurality of segments that are colored, and at least aportion of the colors of the segments of the colored dial correspond tothe colors of the segments of the sliders.

In an embodiment, the user interface further comprises a graphicalindication of a current credit score, and wherein the executable code isconfigured to update the graphical indication of the calculated creditscore but not to update the graphical indication of the current creditscore.

In an embodiment, the user interface further comprises a graphicalcomparative indicator of whether the current credit score is greaterthan, equal to, or less than the calculated credit score, and whereinthe executable code is further to update, in real time, the graphicalcomparative indicator.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram showing a credit score simulation computingsystem, as used in an embodiment.

FIG. 2 is a hierarchical block diagram depicting the organization ofcomponents of a score simulation system such as the website, as used inan embodiment.

FIG. 3 is a flowchart of a process of credit score simulation, as usedin an embodiment.

FIG. 4 is a sample user interface for analyzing score simulations, asused in an embodiment.

FIG. 5 is a block diagram representing a sample data structure of acredit score simulation scenario, as used in an embodiment.

FIG. 6 is a flowchart of a process of construction of a score simulationuser interface as performed on a server, as used in an embodiment.

FIG. 7 is a flowchart of a process of displaying a credit scoresimulation user interface, as used in an embodiment.

FIG. 8 is a sample user interface for simulating credit scores, as usedin an embodiment.

FIGS. 9A and 9B show the user interface of FIG. 8 in alternateconfigurations, as used in an embodiment.

FIG. 10 is a block diagram representing a sample data structure for userinterface elements for score simulation, as used in an embodiment.

FIG. 11 is a flowchart of a process of providing a credit scoresimulation user interface, as used in an embodiment.

FIG. 12 is a flowchart of a process of displaying a credit scoresimulation user interface, as used in an embodiment.

FIGS. 13A-D are sample user interfaces presented on a mobileapplication, as used in an embodiment.

FIG. 14 is a block diagram of a computing system, as used in anembodiment.

DETAILED DESCRIPTION

FIG. 1 is a block diagram of an embodiment of a credit score simulationcomputing system, in conjunction with related components. Credit scoresimulation system 101 may be a single computing device or a plurality ofcomputing devices connected by a network or distributed computingsystem.

In an embodiment, various software modules are included on credit scoresimulation system 101, which may be stored on the system itself, or oncomputer readable storage media separate from the system and incommunication with the system via a network or other appropriate means.The credit score simulation system 101 may include a data collectionmodule 102, which performs various tasks of gathering data used by thecredit score simulation system. Such data may include, for example,credit data 103 retrieved from credit bureau 104. The credit data 103may be retrieved via a network, via a dedicated communication channel,or by other means. In an embodiment, credit bureau 104 transmits creditdata 103 to the credit score simulation system 101 via a securedcommunication channel to ensure the privacy and security of the creditdata.

In an embodiment, credit data 103 is gathered on demand as required bycredit score simulation system 101. In another embodiment, credit data103 is gathered on a periodic basis independent of requests forinformation to the credit score simulation system 101. In anotherembodiment, credit data 103 is stored on the credit score simulationsystem 101, in which case, retrievable of credit data 103 from a creditbureau 104 may not be necessary. In another embodiment, credit data 103is entered by a user rather than retrieved from a credit bureau.

Data collection module 102 may also gather score simulation modelsand/or algorithms 105 from a score simulation data store 106. The scoresimulation models and algorithms may include formulas, executable code,web browser code, JavaScript code, statistical parameters, statisticalvariables, and the like. In an embodiment, the models and/or algorithms105 are retrieved from score simulation data store 106 on an on-demandbasis as needed by the credit score simulation system 101. In anotherembodiment, the models and/or algorithms 105 are retrieved on a periodicbasis. In another embodiment, the credit score simulation system 101internally stores the models and/or algorithms 105, in which case aseparate score simulation data store 106 may not be required.

The credit score simulation system 101 may also include a simulationmodule 109, which may include executable instructions for performingcredit score simulations. Various algorithms for performing suchsimulations of credit scores are described throughout the specification.Further algorithms and disclosures of score simulation techniques andalgorithms are presented in the related applications that areincorporated by reference.

Simulation module 109 may use data retrieved by data collection module102, such as credit data 103 and/or models and/or algorithms 105, asinput to the simulation. Furthermore, simulation module 109 may interactwith one or more end users 107 via a network 108. In variousembodiments, network 108 may be the Internet, a local area network, awide area network, a telecommunications network, a cellular telephonenetwork, a standard telephone network, or the like.

In an embodiment, simulation module 109 may receive one or moreparameters from end user 107. Such parameters may indicate personalinformation about the end user which simulation module 109 may use todetermine appropriate credit data 103 to be applied or retrieved.Furthermore, simulation module 109 may receive, from end user 107,requests to simulate a credit score based on certain user-definedparameters.

In an embodiment, the credit score simulation system 101 furtherincludes user interface module 110, which may include executableinstructions for constructing user interfaces or otherwise interactingwith end users 107. User interface module 110 may receive data from datacollection module 102 and/or simulation module 109, and use that data toconstruct user interfaces that may embody, for example, the results of acredit score simulation. Those interfaces may then be communicated toend user 107. Such simulations may be presented to the end user viavarious user interfaces designed to be easily manipulated and/orunderstood by the user. In an embodiment, the user interfacestransmitted by user interface module 110 are interactive. Variousembodiments of the user interfaces that may be provided by userinterface module 110 are shown and described throughout thisspecification. Variations on such interfaces and other possibleinterfaces will be known to those of skill in the art. For example, userinterface module 110 may provide a telephone or voice-activated commandinterface, a SOAP or REST API, a desktop computer application interface,or the like.

User interface module 110 may be configured to construct user interfacesof various types. In an embodiment, user interface module 110 constructsweb pages to be displayed in a web browser. The web pages may, in anembodiment, be specific to a type of device, such as a mobile device ora desktop web browser, to maximize usability for the particular device.In an embodiment, user interface module 110 may also interact with aclient-side application, such as a mobile phone application or astandalone desktop application, and provide data to the application asnecessary to display credit score simulation information.

FIG. 2 is a hierarchical block diagram showing an organization for ascore simulation system. In an embodiment, the score simulation systempresents a website comprising a number of web pages organized in thefashion shown in FIG. 2. In other embodiments in which interfaces otherthan web pages are used, similar organizational structures may beapplied as is appropriate to the particular means of communication. Forexample, in a telephone-based system, the organization of FIG. 2 may beembodied as an automated telephone response tree.

In an embodiment, credit score simulation system 101 includes twointerfaces: a public user interface 201 and an administrative interface202. In an embodiment, the public user interface is accessible by anyuser in communication with score simulation system 101 whileadministrative interface 202 is only accessible to particularindividuals such as administrators. In an embodiment, administrativeinterface 202 may be protected by a password, by IP-basedauthentication, or by other means.

Public user interface 201 may include one or more modules that may beaccessed by users. The users accessing public user interface 201 may bethe consumers themselves. Alternatively, the users accessing public userinterface 201 may be entities interested in particular consumers. Forexample, a bank or landlord may access public user interface 201 toperform credit score simulation on a prospective loan recipient ortenant.

In various embodiments, the public interface may include anauthenticated section that may be accessed only by authenticated users,such as members who have signed up for an account and/or paid a fee suchas a subscription fee. The public interface may further include anunauthenticated section that may be accessed by users regardless ofauthentication status, or that may be accessed by unauthenticated users.The authenticated and unauthenticated sections may have the samefeatures, similar features, or different features. In an embodiment, theauthenticated section offers additional features not available in theunauthenticated section. For example, credit data or credit-relatedinformation is used in the various systems and methods described herein.This information be stored in member accounts or automatically retrievedbased on member account data. In such an embodiment, the credit-relatedinformation may be automatically pre-populated, so that members need notenter that information, while unauthenticated users would enter theirinformation manually.

Public user interface 201 includes a scenario simulation section 203which may enable the user to view various predetermined scenarios anddetermine simulated credit scores associated with those variousscenarios. An embodiment of a user interface presented by such a sectionis shown in FIG. 4. Public user interface 201 may further include anadjuster simulation section 204 which may enable the user to view creditscores and interactively adjust parameters that affect that score. Anembodiment of a user interface presented by such a section is shown inFIG. 8. Public user interface 201 may further include other simulationsection 205. In various embodiments, public user interface 201 mayinclude all of these sections, some of these sections, and/or othersections as may be contemplated by those of skill in the art.

Administrative interface 202 may also comprise various sections. Forexample, it may include a scenario management section 206 where anadministrator to the system may add, remove or modify various scoresimulation scenarios. In an embodiment, input relating to the scenariosmanaged using interface section 206 affects the scenarios presented insection 203 of the public user interface. Administrative interface 202may also include an adjuster management section 207 which similarly maybe used to effect the adjuster simulation section 204 of the public userinterface. Administrative interface 202 may also include othermanagement features 208 or may include fewer features. Additionally,administrators to the system may find it useful to review statistics orother information relating to the usage of the credit score simulationsystem. Such information may be provided using data reporting section209 of the administrative interface. In various embodiments, othersections or fewer sections may be included in the administrativeinterface 202. In an embodiment, no administrative interface isprovided.

FIG. 3 is a flowchart of a process of credit score simulation as used inan embodiment. The process may be performed, for example, by a creditscore simulation system 101 of FIG. 1, or by other suitable computingsystems. In an embodiment, the process shown in FIG. 3 may be performedsubstantially in real time so that the user requesting information ispresented with that information without substantial delay. In variousembodiments, fewer blocks or additional blocks may be included in theprocess, or various blocks may be performed in an order different fromthat shown in FIG. 3.

At block 301, the system receives credit-related information from a userand/or third parties. Such information may include personal identifyinginformation enabling the system to determine the identity of the user oranother individual. The information may further enable the system toretrieve credit data associated with the appropriate individual.Furthermore, such information may include the public data as retrievedfrom a credit bureau or other credit information source. In anembodiment, the credit data retrieved is a credit score. In anembodiment, the credit information retrieved is credit data from aconsumer's credit history that the system 101 may use to calculate acredit score for the consumer, such as based on a credit score model ofa credit bureau or based on a credit score model that is configured toapproximate credit scores provided by one or more credit bureaus.Further data may be retrieved by the system and incorporated into theprocesses described herein.

At block 302, the system constructs one or more credit score simulationparameters and/or other data. These parameters may be used by the systemto simulate a credit score. For example, such data may include thecredit score itself, which may be calculated using credit data of theconsumer. Additional parameters relating to the consumer's credit usagemay be calculated as well. For example, the system may use credit datato calculate aggregate or average information, such as the averagecredit balance for the consumer or the average number of months latethat the consumer pays off credit card debt.

In an embodiment, the data constructed at block 302 may includeinformation on how much a particular consumer's credit score would beaffected by various activities. In an embodiment, the data may includeinformation about types of actions that may be taken by the individualwhose credit score is being simulated. This information may be based onparticular personal information associated with the individual. Forexample, the system may determine that a consumer has no credit cardsbased on, for example, information received at block 301. In such acase, at block 302, the system may determine that it is not possible forthe user to pay off the consumer's credit card debt and thus, the systemwill not recommend doing so.

In an embodiment, the data constructed at block 302 may include summaryinformation associated with the user's credit behavior. Such informationmay be derived from the user's credit report, may be received directlyfrom the user, or may be gathered by other means. Other such parametersmay be constructed at block 302.

At block 303, the system applies one or more credit score simulationmodels to determine a simulated credit score. Various score simulationmodels may be used. Some of such models are disclosed throughout thisspecification and in the related applications that are incorporated byreference. In various embodiments, the score simulation model mayincorporate information about the consumer's actual credit score, or itmay estimate the consumer's credit score based on user providedinformation alone and/or other information, without relying on an actualcredit score. In an embodiment, the score simulation model may be basedon various statistical models such as linear regression, non-linearregression, neural networks, and the like. The results of applying thescore simulation model at block 303 may include one or more simulatedcredit scores and possibly other information, which may include, forexample, recommendations for possible actions to be taken, ranges ofcredit scores, possible parameters for adjustment, and so on.

At block 304, the system uses the results of the score simulation modelfrom block 303, as well as other information, to construct userinterface data. The user interface data may take on various formsdepending on the particular means of communication with the user whoinitiated the request. In various embodiments, the user interface datamay be web page data, application-specific data, mobile applicationdata, or other such graphical data. In other embodiments, the userinterface data may not be visual data, but rather be audio data, XMLdata, comma-separated values (CSV) data, and so on.

At block 305, the user interface data constructed at block 304 may betransmitted to the user, who may be the consumer or other entity. Atblock 306, the user may use the user interface to adjust varioussimulation parameters. This may be done, for example, via an interactiveuser interface that provides various controls configured to bemanipulated by the user. The interface may be configured to convertthose user manipulations into data that may be transmitted back to thescore simulation system.

At block 307, the adjusted parameters are transmitted to the system, andthe system receives a request to adjust parameters. Upon receiving therequest to adjust the parameters, the system further may perform varioussteps in the process of FIG. 3 to calculate updated credit scoresimulation values and provide the user with further user interface data.In an embodiment, the system distinguishes between the initialtransmission of user interface data and subsequent transmissions of userinterface data so that it may transmit only portions that are necessaryto update the user interface data in the latter case. This may be done,for example, using an XMLHttpRequest (XHR) mechanism, a data pushinterface, or other communication protocols.

FIG. 4 is a sample user interface, as presented by an embodiment of thecredit score simulation system. In various embodiments, the userinterface shown in FIG. 4 may be presented as a web page, as a mobileform application, as a stand-alone application, or by othercommunication means. In other embodiments, analogous interfaces may bepresented using audio or other forms of communication. In an embodiment,the interface shown in FIG. 4 is configured to be interactive andrespond to various user interactions. Such user interactions may includeclicks with a mouse, typing with a keyboard, touches and/or gestures ona touch screen, voice commands, and/or the like.

The user's current credit score may be displayed on the user interfaceusing interface element 401. This credit score may be an actual creditscore or an estimated credit score provided based on informationsubmitted by the user. In addition to the user's numeric credit score,the interface may optionally or alternatively present a graphical and/ortextual representation of the user's credit rating 402. In anembodiment, the graphical representation of the rating may include adial with a pointer indicating the user's relative credit risk. In anembodiment, a textual representation may include a textual descriptionof the user's credit risk rating such as “Very Low Risk.” Both agraphical and a textual representation may be included, or only one, orneither, in various embodiments.

In an embodiment, the interface may include a listing or other displayof various scenarios 403, representing possible actions that maypotentially affect the consumer's credit score. The scenarios 403 listedin FIG. 4 may be a predefined list of scenarios displayed for everyconsumer whose information is displayed by the system. Thus, because thesame scenarios are used for each consumer, the consumer's credit rating402 may be located at different locations between the predefinedscenarios 403. As shown in FIG. 4, the interface includes scenarios 403a that would cause a decrease in credit score of the consumer, as wellas scenarios 403 b that would cause an increase in the credit score ofthe consumer.

In another embodiment, the scenarios are selected based on informationrelating to the consumer. For example, the system may omit particularscenarios that are not applicable to the consumer's situation, asdetermined based on the consumer's credit history or other personalinformation. In other embodiments, the system may identify actions thatare particularly relevant to the consumer and graphically highlight orotherwise identify them. In an embodiment, the selected scenarios arechosen based on factors such as scenarios of the most interest to thegeneral public, the level of impact on the simulated credit score (forexample, selecting scenarios having the most impact), scenarios relevantto the consumer based on the consumer's credit history or spendinghabits, and/or other factors.

In an embodiment, a subset of scenarios is initially displayed, and thenan expanded list of scenarios may be optionally shown upon user request.For example, if the system determines that a consumer could easily payoff credit card debt but would have more difficulty paying off a homemortgage, then the system may highlight the scenario of paying offcredit card debt, and/or it may omit or hide the home mortgage paymentscenario. In an embodiment, the user may be provided options to add inscenarios that are not selected to be displayed, or to remove scenariosthat are displayed, thus making the user interface customizable by theuser.

In an embodiment, the scenarios are presented in association with anindication of an estimated credit score that would potentially resultshould the user perform the associated action. The simulated creditscore may be calculated based on data maintained by the system relatingto the action, and it may be further based on credit informationassociated with the particular user. The simulated credit score may becalculated using various score simulation models, as explainedpreviously in this disclosure.

In an embodiment, each scenario is displayed with a numeric estimatedscore 404 and a graphical indication 405 of the simulated score. Forexample, as shown in FIG. 4, the graphical representation 405 mayinclude an up arrow, down arrow, or equal sign indicating the relativechange that the scenario would have on the user's credit score. In anembodiment, to further improve the user's ability to understand the userinterface of FIG. 4, the graphical representations 405 are colored toreflect the relative effect the action will have on the user's creditscore. For example, actions that would increase the user's credit scoremay be colored green, whereas actions that would decrease the user'scredit score may be colored red.

In an embodiment, the listing of scenarios 403 may further be sorted invarious orders, such as by the estimated credit scores 404. The user maybe able to select the order in which the scenarios are sorted. In anembodiment, the interface element 401 showing the user's actual creditscore is inserted into the list of scenarios 403 in an appropriatelocation relative to estimated scores 404. In other embodiments, theinterface element 401 showing the actual score may be placed on otherparts of the user interface.

The display shown for each scenario may further include extended and/oradditional information 407 relating to the particular scenario. In anembodiment, to improve the appearance of the user interface, suchadditional information may be hidden and only displayed in response toan appropriate user interaction with the user interface. For example, inthe embodiment shown in FIG. 4, the user may use interface elements 406,for example by clicking on it, to display additional information.

The display of additional information 407 may include any additionalinformation that may be associated with the particular selectedscenario. For example, the scenario associated with additionalinformation 407 is the scenario of making all payments on time for thenext six months. The additional information includes a textualdescription of the scenario 408 as well as further score simulations 409for time frames different from six months. This provides the user witheasy access to further credit score simulations for related scenarios.

Additionally, the display of additional information 407 may include oneor more graphical and/or textual descriptions of credit scoresimulations 409 for the selected scenario and/or for the extendeddisplays of related scenario. For example, dials indicating the relativesimulated credit score may be shown for the selected scenario, for anyor all of the related scenarios in the extended information, for both,or for neither. Additionally, in an embodiment, the additionalinformation 407 may include one or more links 410 to further informationrelating to the selected action.

The user interaction employed to display additional information 407 maybe, for example, a mouse click, a tap or gesture on a touch screen, akeyboard selection, a drag and drop operation, voice command, or otherform of interaction. In an embodiment, when a user requests to displayadditional information for one particular action, any other displays ofadditional information are automatically hidden thereby reducing clutteron the user interface. In other embodiments, additional information 407may always be displayed or may never be displayed.

The location at which additional information 407 is placed may also varyin various embodiments. For example, as shown on FIG. 4, additionalinformation 407 may be displayed underneath the particular selectedaction. In another embodiment, additional information 407 may be shownin an internal window within the user's web browser or otherapplication. In other embodiments, the additional information 407 may beshown in a separate pop-up window. In another embodiment, the additionalinformation 407 may be shown on a separate web page.

One example of a scenario that may be included on the interface of FIG.4, in an embodiment, is whether the individual accepted a pre-approvedcredit card offer with a particular credit limit. The particular creditlimit may be $2,500, $5,000, $10,000, $15,000, or $20,000, or any otheramount, in various embodiments. The expanded scenarios associated withthis scenario may be based on any subset of these credit limit amounts,or all of the amounts, or further amounts.

Another example of a scenario that may be included on the interface ofFIG. 4 is whether the individual makes all payments on time for aparticular number of months into the future. The number of months may be6 months, 12 months, 18 months, 24 months, or any other number, invarious embodiments. The expanded scenarios associated with thisscenario may be based on any subset of these numbers of months, or allof the numbers, or further numbers.

Another example of a scenario that may be included on the interface ofFIG. 4 is whether the individual consolidates all of his/her majorcredit card balances onto one major credit card with a particular creditlimit. The particular credit limit may be $2,500, $5,000, $10,000,$15,000, or $20,000, or any other amount, in various embodiments. Theexpanded scenarios associated with this scenario may be based on anysubset of these credit limit amounts, or all of the amounts, or furtheramounts.

In order to generate the listing of various actions as shown on FIG. 4,the system may include a database or other data store of informationrelating to possible actions. An example of a data structure that may beemployed to store such information about actions and/or scenarios isshown on FIG. 5. In various embodiments, the system may includeadditional information or less information in such a data structure. Thedata structure may be stored in any number of formats such as arelational database, XML data, HTML data, common separated values (CSV)data, or other formats.

In the embodiment shown in FIG. 5, one or more score simulation scenariodata records 501 may be stored by the system. Each score simulationscenario data record may include a number of elements. For example, eachrecord may include a textual description of the scenario 502. Thistextual description may be used in the listing of possible actions asshown in FIG. 4.

The score simulation scenario data structure 501 may further include oneor more parameter adjustment rules 503. Such rules may be used todetermine the appropriate simulated credit score to be associated withthe scenario or action. For example, for a scenario of making allpayments on time for the next six months, the parameter adjustment rules503 may indicate how much a credit score would change should such anaction be taken. The adjustment rules may account for the user's actualcredit information in performing the adjustment of the credit score.

In an embodiment, the parameter adjustment rules comprise executablecode that recalculates the estimated credit score. In anotherembodiment, the parameter adjustment rules comprise data relating to howto adjust parameters to be provided to one or more score simulationmodels and the score simulation models apply the parameter adjustmentrules 503 to calculate the new simulated credit score.

The score simulation scenario data structure 501 may further includedata relating to expanded simulation scenario data 504. This data may beused, for example, to calculate the information for the expanded displayof additional information 407 shown in FIG. 4. In an embodiment, theexpanded simulation scenario data 504 may include similar data elementsto that of the score simulation scenario data structure 501. Forexample, it may include descriptive text and/or further parameteradjustment rules for each of the expanded simulations. In an embodiment,for example, the expanded simulation scenarios may include making allpayments on time for the next six months, one year and two years. Thus,in this embodiment, the expanded simulation scenario data 504 mayinclude descriptive text and parameter adjustment rules for each ofthose three possible expanded scenarios.

FIG. 6 is a flowchart of a process of constructing a scenario-basedcredit score simulation interface. For example, the process shown inFIG. 6 may be used to construct an interface such as that shown on FIG.4. In an embodiment, the process shown on FIG. 6 may be performed by oneor more computing systems such as the credit score simulation system 101of FIG. 6. In various embodiments, some of the blocks of FIG. 6 may notbe performed, other blocks may be included, and/or blocks may beperformed in an order different from that shown.

At block 601, the system accesses credit information associated with aparticular consumer. The credit information may be retrieved from acredit bureau, may be stored locally on the score simulation system, maybe entered by a user such as the consumer, or may be maintained and/orretrieved from other sources.

At block 602, the system calculates or accesses a credit score andrelated information associated with the consumer. In an embodiment, thesystem retrieves a credit score directly from a credit bureau or fromanother source. In another embodiment, the system retrieves credit dataand uses that credit data and a credit score model to calculate thecredit score for the consumer. Additionally, further data may becalculated or accessed at block 602. Such data may be useful, forexample, in constructing the user interface for the particularconsumer's situation. For example, data on the consumer's history ofcredit card payments may be accessed or calculated in order to presentactions and/or scenarios that are appropriate to that consumer's historyof credit card payments.

At block 603, the system may retrieve a list of credit score simulationscenarios. This list may be accessed and/or derived from one or moredata structures such as the data structure shown in FIG. 5. In anembodiment, the system retrieves a predefined set of scenarios that areused for all consumers. In an embodiment, the predefined set ofscenarios is configured to provide most consumers with at least somescenarios that would decrease the consumer's credit score, and at leastsome scenarios that would increase the consumer's credit score. Forexample, some of the scenarios may be actions that are generally knownto increase credit scores (e.g., paying off outstanding debts), whilesome of the scenarios may be actions that are generally known todecrease credit scores (e.g., making late payments). In an embodiment,the system may not need to retrieve the scenarios since the samescenarios are used for all consumers, but may rather have the predefinedset of scenarios stored locally on the system or even directly encodedin software.

In another embodiment, the system determines a subset of scenarios thatare appropriate to the particular consumer's situation. This may bebased, for example, on the credit score and related information that wascalculated or accessed at block 602.

At block 604, the system selects a scenario from the list of scenariosretrieved at block 603. At block 605, the system calculates a simulatedcredit score based on the consumer credit information accessed at block601 or calculated at block 602 and further based on data associated withthe selected scenario. The simulated credit score may be calculatedbased on one or more statistical models available to the scoresimulation system, or by other means described elsewhere in thisspecification or known to those of skill in the art. Thus, the systemmay recalculate the simulated credit score for the scenario using creditdata of the consumer, with some data elements replaced with data for theparticular scenario being processed.

At block 606, the system optionally calculates simulated credit scoresfor expanded scenarios. These calculations may be used to display theadditional information associated with particular actions or scenarios.The credit scores for expanded scenarios may be calculated in the sameway described with respect to block 605, or by other means.

In an embodiment, the simulated credit scores for expanded scenarios arecalculated prior to transmitting data to the user. In anotherembodiment, the system does not calculate simulated credit scores forthe expanded scenarios, and instead waits to receive appropriaterequests from the user before calculating simulated credit scores forthose expanded scenarios. Thus, the processes of block 606 may beperformed at various times in different embodiments.

At block 607, the system determines whether there are further simulationscenarios in the list of simulation scenarios retrieved at block 603. Ifthere are, then the system returns to block 604 and further performscalculations of simulated credit scores for each of the other scenarios.If not, then at block 608, the system constructs user interface data orother data, based on the calculated credit scores and/or otherinformation calculated or retrieved by the system. At block 609, theconstructed user interface data is transmitted to a user computer.

FIG. 7 is a flowchart of a process of displaying simulation scenarios asused in an embodiment. Such a process may be performed on a clientcomputer that is displaying a user interface such as that shown in FIG.4. In an embodiment, parts or all of the process shown in FIG. 7 may beperformed using executable code, such as JavaScript code, sent by thescore simulation computer (e.g. a server) to a client computer browserin combination with the web page.

At block 701, the system displays a listing of credit scores simulationscenarios. Such a listing may appear like listing 403 of FIG. 4. Atblock 702, a user selection of a simulation scenario is received. Such aselection may be, for example, a mouse click on a web page. The userselection may indicate a particular scenario that has been selected ormay indicate several scenarios to be selected.

At block 703, the client computer optionally sends a request to thescore simulation server for expanded scenario information. At block 704,the expanded scenario information is received by the client computer. Inorder to do this, the score simulation system may be configured toreceive such requests for expanded scenario information and to transmitthat appropriate data indicating the expanded score simulation scenarioinformation. This expanded information may be in the form of userinterface data such as web page data, or it may simply include numericcredit scores or other raw information that may be formatted by theclient's computer web browser in accordance with the executable code.

In another embodiment, the expanded scenario information is alreadyavailable to the client computer without performing blocks 703 and 704.This may be the case, for example, where the expanded score simulationscenario information was pre-calculated and transmitted in conjunctionwith the user interface data that was displayed at block 701. Forexample, if optional block 606 of FIG. 6 was performed, then the clientcomputer may already have received the expanded scenario information. Insuch a case, blocks 703 and 704 may not need to be performed. In anotherembodiment, the client computer performs blocks 703 and 704 the firsttime a user selects a particular scenario at block 702 but it caches theresult received at block 704, so that it need not perform block 703 and704 again the next time the user selects that same scenario.

At block 705, the client computer displays the expanded scenarioinformation. This display may be presented using any number of formssuch as an expanded display on the window, on internal window within theweb browser, a separate pop-up window, a separate web page or tab, orother means. In an embodiment, the user interface is configured toanimate the display of the expanded scenario information.

FIG. 8 is a sample user interface for credit source simulation as usedin an embodiment. In this user interface, the user's current creditscore may be shown at interface elements 801 and a graphical and/ortextual representation of the user's credit score may be presented usinginterface element 802. Additionally, a simulated credit score may bepresented using interface elements 803 and 804. When the user interfaceis initially transmitted to the client computer, the simulated scoredisplays 803 and 804 may be equal to the actual score displays 801 and802.

The user interface further includes one or more credit scores simulationadjusters 805. These adjusters enable the user to modify parameters tobe provided to the credit score simulation system and allow it tocalculate further simulated credit scores. In an embodiment, thesimulation adjusters 805 are graphical sliders including a display of abar 806 and a handle 807 configured so that the user may adjust handle807 across bar 806, for example by clicking and dragging it so as toslide it.

In an embodiment, bar 806 comprises a plurality of segments associatedwith different values to be provided to the credit score simulationsystem. For example, bar 806 is divided into sections, each sectionrepresenting different portions of credit use such as 65-100% 808,52-64% 809, 30-51% 810, 16-29% 811, and 0-15% 812.

In an embodiment, handle 807 is initially placed within the segment ofbar 806 that most closely reflects the user's actual credit information.For example, handle 807 is initially placed within region 811 becausethe user whose credit score is being simulated in the interface of FIG.8 has a credit usage value of 16-29%.

In an embodiment, each of the segments 808 through 812 is colored toreflect a credit risk associated with that segment. In an embodiment,the colors are selected to correspond with those colors used in thegraphical display 802 and 804. For example, a credit used amount of65-100% may create a high credit risk and as a result, section segment808 may be colored the same as the high risk section of elements 802 and804. In an embodiment, segment 808 is colored red and segment 812 iscolored green, to indicate that segment 812 indicates a low risk whilesegment 808 represents a high risk. As shown in the example of FIG. 8,not all sliders include all risk categories and the risk categories arenot uniform for all sliders.

In an embodiment, the segments of bar 806 and the other interfaceelement 805 are created automatically by the credit score simulationsystem and remain positioned where they are regardless of the user'sadjustment of handle 807 or other manipulations of the user interface.In other embodiments, the segments may be adjusted in response to theuser adjusting one or more of the interface element 805. For example, ifthe user moves handle 807 to indicate a different amount of credit use,this may cause other sliders or interface elements to change theircolored segments and/or handles.

In an embodiment, changing the value of one or more of the simulationadjusters results in a corresponding change to the display of thepotential score 803 and 804. This is shown in detail in FIGS. 9A and 9B.

In FIG. 9A, the user has moved handle 807 into region 810 of slider bar806. In response, the user interface element 803 displaying thesimulated credit score has been updated to reflect a new simulatedcredit score. Additionally, display 804 has been updated to graphicallyindicate the changed simulated credit score. While in FIG. 8 element 804showed a very low risk for the user, in FIG. 9A, as a result of thechange of the value for bar 806, element 804 displays an average riskfor the user. These updates may be performed substantially in real time,so that there is minimal delay or no delay between the user movinghandle 807 and the simulated credit score values being updated. In thisway, the consumer is provided with a graphical indication of how variouschanges affect their risk level.

In FIG. 9B, handle 807 has been further moved into segment 808 of bar806. Accordingly, the simulated score 803 and graphical display of thesimulated score 804 have been further updated to reflect the newsimulated score and a high risk category.

Although the user interface has been described with respect to sliderinterface elements, other user interface elements may be used in variousembodiments. For example, the user may select items off of a list,rotate a dial, type in information, or otherwise interact with the userinterface. Additionally, the user interface may include variousgraphical, textual, and other indications of changes, in addition to, orrather than, updating the simulated score 803 and graphical display 804.For example, the “vs” symbol between the current score and simulatedscore may be colored to reflect the difference between the scores. In anembodiment, the “vs” symbol is colored red when the potential score islower than the current score, yellow when the scores are equal, andgreen when the potential score is higher than the current score. Invarious embodiments, audible and/or tactile feedback may further beprovided based on the simulated score.

The credit score simulation system maintains information about each ofthe adjuster elements such as slider shown in FIG. 8. The informationfor these adjuster interfaces may be stored in data structures such asthose shown in FIG. 10. Each adjuster interface element data structure1001 may include various information associated with the particularsimulation adjuster interface elements. For example, it may includeparameter adjustment rules 1002. These adjustment rules indicate how asimulated credit score should be adjusted for various values presentedby the simulation adjuster interface elements.

Additionally, the data structure may include a range of adjustmentvalues 1003 indicating what values the adjuster interface element maytake on. The range of adjustment values may be a continuous range with aminimum and maximum value, or it may be a discrete set of particularvalues. Additionally, the data structure may include a description 1004and/or other information useful in displaying the simulation adjustmentinterface element.

FIG. 11 shows a flowchart of a process of constructing a user interfacesuch as that shown in FIG. 8. The process may be performed by a creditscore simulation system 101 of FIG. 1 in an embodiment.

At block 1101, the system provides multiple simulation controls such asslider positions at the parameter values associated with a particularuser's information. These controls may be provided via an interface suchas that shown in FIG. 8. At block 1102, the system receives one or morechange simulation control values. This change to simulation controlvalues may be based on user interactions with the simulation controls.Such interaction may include, for example, sliding the handle on one ormore slider bars.

At block 1103, the system determines a simulated credit score based onthe depicted change to the simulation control values. The simulatedcredit score may further be based on actual credit informationassociated with the user including the user's actual credit score.

At block 1104, the system determines a risk category associated with thesimulated credit score calculated at block 1103. The risk category maybe based on internal data relating to risk categories for particularcredit scores or range of the credit scores. At block 1105, the systemconstructs an updated user interface illustrating the simulated creditscore calculated at block 1103 and the associated risk categorycalculated at block 1104. The constructed user interface may be acomplete user interface such as that shown in FIG. 8, or only a portionof the user interface that requires updating.

In an embodiment, if the system determines at block 1104 that the riskcategory has not changed, then block 1105 may be omitted. In anotherembodiment, the system may only construct information or instructions toupdate the user interface and the actual updating of the user interfacemay be performed by an application such as a web browser on the clientcomputer. In such a case, blocks 1104 and 1005 may need not be performedat all.

At block 1106, the system transmits updated user interface data or otherdata to the client computer. The updated data may be used then by theclient computer to update the displayed user interface so that the usermay see the new simulated credit score.

FIG. 12 is a flow chart of a process of displaying a user interface withmultiple simulation control such as that shown in FIG. 8 as used in anembodiment. At block 1201, the system displays source simulation data.This data may be displayed in an interface such as that shown in FIG. 8.At block 1202, the user manipulates the user interface to adjust one ormore user interface elements. The interaction may be performed by one ormore mouse clicks, touches or gestures on a touch screen, drag and dropoperations, keyboard inputs, voice commands, or other mechanisms. Theclient computer then determines appropriate simulation parameters basedon the adjusted interface elements.

In various embodiments, the client computer may then proceed to performeither block 1203, block 1204, or a combination thereof. At block 1203,the client computer transmits a request to the credit score simulationsystem including values associated with the adjusted interface elements.The request may include data indicating those adjusted interfaceelements using a variety of formats in accordance with the protocolunderstood by the credit score simulation system. In response, thecredit score simulation system may transmit updated user interface dataor other data to the client computer.

Alternatively, at block 1204, the client computer may calculate anupdated simulated credit score and/or other information usingclient-side code such as JavaScript code. In such an embodiment, theclient computer does not need to communicate with the credit scoresimulation server which provides some possible performance benefits tothe user of the client computer.

In an embodiment, rather than calculating an updated score at eitherblock 1203 or 1204, only a score delta value is calculated, indicatingnot the resulting simulated credit score but a difference between theactual credit score and the simulated credit score. Executable code onthe client computer or score simulator system may then be configured toupdate the user interface to reflect the simulated credit score,calculated based on the actual credit score and the delta value.

At block 1205, the system updates the overall score display of the userinterface. Such updating may involve, for example, displaying a newsimulated credit score and/or updating graphical or textualrepresentations of the associated credit risk. In an embodiment, theupdates of the overall score display is performed substantially in realtime so that there is minimal delay between the adjustment of the userinterface elements and the update of the score display. This provides abenefit to the user of being able to immediately view the effect ofchanges to the various interface elements.

FIGS. 13A-D are sample user interfaces on a mobile device, as used in anembodiment. In various embodiments, all of these interfaces, a subset ofthese interfaces, and/or additional interfaces may be presented. In amobile context, the credit score simulation system may communicate witha dedicated application executing on a mobile or other computing device,or it may transmit web page data or other data that may be understood bythe mobile device. The user interfaces presented by the mobile devicemay be similar to the web page interfaces described above, or they maybe adjusted to comport with the specifications and features of thedevice. Additionally, the manner in which the user interacts with themobile application may be different, in some embodiments. For example,the user may use touch screen input such as gestures to control theinterface, rather than mouse input.

Example System Architecture

FIG. 14 is a block diagram illustrating one embodiment of a system thatmanages calendar data. In the embodiment of FIG. 14, a computing device1401 is in communication with a user 1402, as well as an optionalthird-party data source 1403, via a network 1404. In an embodiment, thecomputing device 1401 receives data, such as credit data, from one ormore data sources 1403 and accesses the data to identify informationregarding one or more entities. The computing device 1401 may thenperform analysis and prepare information for presentation to the user1402. The credit score simulation system 101 may include the same orsimilar components as the computing device 1401. Similarly, thecomputing devices 1401 may be used to implement any of the methodsdiscussed herein.

The network 1404 may include any communication network or combination ofcommunication networks, such as one or more of the Internet, LANs, WANs,MANs, etc., for example. In the embodiment of FIG. 14, the computingdevice 1401 includes a computing system having one or more computingdevices (e.g., computers). The computing device 1401 may include, forexample, a single computing device, a computer server, a smart storageunit, or a combination of one or more computing devices and/or computerservers. Depending on the embodiment, the components illustrated in thecomputing device 1401 may be distributed amongst multiple devices, suchas via a local area or other network connection. In other embodimentsthe computing device 1401 may include fewer and/or additional componentsthat are illustrated in FIG. 14.

The exemplary computing device 1401 may be a general purpose computerusing one or more microprocessors, such as, for example, an Intel®Pentium® processor, an Intel® Pentium® II processor, an Intel® Pentium®Pro processor, an Intel® Pentium® IV processor, an Intel® Pentium® Dprocessor, an Intel® Core™ processor, an xx86 processor, an 8051processor, a MIPS processor, a Power PC processor, a SPARC processor, anAlpha processor, and so forth. The computer may run a variety ofoperating systems that perform standard operating system functions suchas, for example, opening, reading, writing, and closing a file. It isrecognized that other operating systems may be used, such as, forexample, Microsoft® Windows® 3.X, Microsoft® Windows 98, Microsoft®Windows® 2000, Microsoft® Windows® NT, Microsoft® Windows® CE,Microsoft® Windows® ME, Microsoft® Windows® XP, Windows® 7, Palm PilotOS, Apple® MacOS®, Disk Operating System (DOS), UNIX, IRIX, Solaris,SunOS, FreeBSD, Linux®, or IBM® OS/2® operating systems. In otherembodiments, the computing device 1401 may be controlled by aproprietary operating system. Conventional operating systems control andschedule computer processes for execution, perform memory management,provide file system, networking, I/O services, and provide a userinterface, such as a graphical user interface (“GUI”), among otherthings.

The computing device 1401 includes one or more central processing units(“CPU”) 1405, which may each include one or more conventional orproprietary microprocessor(s). The computing device 1401 may furtherinclude one or more memories 1406, such as random access memory (“RAM”),for temporary storage of information, read only memory (“ROM”) forpermanent storage of information, and/or a mass storage device 1407,such as a hard drive, diskette, or optical media storage device. Thememory 1406 may store software code, or instructions, for execution bythe processor 1405 in order to cause the computing device to performcertain operations, such as gathering sensor-related data, processingthe data with statistical and/or predictive models, formatting data foruser devices or other presentation, transmitting data, or otheroperations described or used herein.

The methods described and claimed herein may be performed by anysuitable computing device, such as the computing device 1401. Themethods may be executed on such suitable computing devices in responseto execution of software instructions or other executable code read froma non-transitory tangible computer readable medium or computer storagedevice. A computer readable medium is a data storage device that canstore data that is readable by a computer system. Examples of computerreadable mediums include read-only memory, random-access memory, othervolatile or non-volatile memory devices, CD-ROMs, magnetic tape, flashdrives, and optical data storage devices.

The exemplary computing device 1401 may include one or more input/output(I/O) devices and interfaces 1408, such as a keyboard, trackball, mouse,drawing tablet, joystick, game controller, touchscreen (e.g., capacitiveor resistive touchscreen), touchpad, accelerometer, and/or printer, forexample. The computing device 1401 may also include one or moremultimedia devices 1409, such as a display device (also referred toherein as a display screen), which may also be one of the I/O devices1408 in the case of a touchscreen, for example. Display devices mayinclude LCD, OLED, or other thin screen display surfaces, a monitor,television, projector, or any other device that visually depicts userinterfaces and data to viewers. The computing device 1401 may alsoinclude one or more multimedia devices, such as speakers, video cards,graphics accelerators, and microphones, for example.

In the embodiment of FIG. 14, the I/O devices and interfaces 1408provides a communication interface to various external devices via thenetwork 1404. For example, the computing device 1401 may beelectronically coupled to the network 1404 via a wired, wireless, orcombination of wired and wireless, communication link(s). The network1404 may allow communication with various other computing devices and/orother electronic devices via wired or wireless communication links.

In the embodiment of FIG. 14, the computing device 1401 may include adata collection module 1410, a simulation module 1411, and a userinterface module 1412, as well as other modules or fewer modules. Eachof these modules is discussed in further detail below. In general, theword “module,” as used herein, refers to logic embodied in hardware orfirmware, or to a collection of software instructions, possibly havingentry and exit points, written in any programming language, such as, forexample, Java, Python, Perl, Lua, C, C++, C#, Objective C, etc. Asoftware module may be compiled and linked into an executable program,installed in a dynamic link library, or may be written in an interpretedprogramming language such as, for example, BASIC, Perl, or Python.Software modules may be callable from other modules or from themselves,and/or may be invoked in response to detected events or interrupts.Software modules configured for execution on computing devices may beprovided on a computer readable medium, such as a compact disc, digitalvideo disc, flash drive, or any other tangible medium. Such softwarecode may be stored, partially or fully, on a memory device of theexecuting computing device, such as the computing device 1401, forexecution by the computing device. Hardware modules may be comprised ofconnected logic units, such as gates and flip-flops, and/or may becomprised of programmable units, such as programmable gate arrays orprocessors. The modules described herein are typically implemented assoftware modules, but may be implemented in hardware, firmware and/orsoftware. Generally, the modules described herein refer to logicalmodules that may be combined with other modules or divided intosub-modules despite their physical organization or storage.

Example Modules

In the embodiment of FIG. 14, the computing device 1401 includes threemodules, namely, a data collection module 1410, a simulation module1411, and a user interface module 1412. In this embodiment, each of themodules is shown as part of the computing device 1401. However, in otherembodiments, the modules may be distributed across multiple devices, andmay be controlled and/or operated by multiple different entities. Thesemodules are configured to perform methods as described throughout thisspecification. In various embodiments, fewer or additional modules maybe included within a computing system.

The computing device 1401 may be configured to acquire user data andother external data such as third-party data. The various modules maycomprise software alone, hardware alone, or a combination of softwareand hardware. The device may be especially adapted to communicate usinga variety of network or communications protocols in order to communicatewith the sensors or external data sources. Some of these protocols mayinclude standard network protocols, such as HTTP, FTP, SNMP, or thelike. The device may further include hardware drivers, such as USB,FireWire, Thunderbolt (Light Peak), or serial communications drivers,for example to communicate with devices in direct communication with thesystem.

The computing device 1401 may be configured to transmit, or initiatetransmission of, data such as user interfaces, data reports, applicationprogramming interface, data, or the like, to requesting entities, suchas external user 1402, that have registered interest with the system. Inone embodiment, the device provides the data in an unformatted datastructure, such as in an XML, CSV, TXT, or other spreadsheet, text, orweb accessible data structure. In other embodiments, the device providesinformation in user interfaces, such as user interfaces that areconfigured for rendering by a web browser, mobile device, tablet device,or other device or application, for display to users. A variety ofdifferent presentations may be provided. In some embodiments, therequesting entities may indicate presentation preferences orconfigurations (e.g., data formats and/or types of information), and thedevice may transmit data based on the indicated preferences orconfigurations. The presentation format may also be determined based onthe type of device being used by the user.

In an embodiment, any or all of the modules 1410-1412 are configured toact in real time. Thus, when data is received by the modules, themodules process that data as soon as practicable or necessary to provideusers with timely information. In order to achieve this, specializedhardware may be used to gain efficiency, and executable code may bedesigned to minimize latency or computation time. In an embodiment, themodules, possibly with other modules of the system, are executed withina real-time operating system, to enhance the responsiveness of thesystem.

Several flowcharts and related methods are described throughout thisspecification. Although each flowchart illustrates a particular quantityof blocks, the methods associated with the flowcharts may include anysubset of illustrated blocks, or may include additional blocks that arenot illustrated. Also, the blocks may be performed in orders differentthan illustrated in the figures. Software code configured for executionon a computing system in order to perform the methods of respectiveflowcharts may be provided on a computer readable medium, such as acompact disc, digital video disc, flash drive, hard drive, memory deviceor any other tangible medium. Such software code may be stored,partially or fully, on a memory of a computing system, in order toperform the illustrated methods by those respective devices. For ease ofexplanation, the methods will be described herein as performed by acomputing system, which should be interpreted to include any one or moreof the computing systems noted above, any combination of those computingsystems, and/or any other suitable computing system.

Although this disclosure has been described in terms of certain exampleembodiments and applications, other embodiments and applications thatare apparent to those of ordinary skill in the art, includingembodiments and applications that do not provide all of the benefitsdescribed herein, are also within the scope of this disclosure.

All publications and patent applications mentioned in this specificationare herein incorporated by reference in their entirety to the sameextent as if each individual publication or patent application wasspecifically and individually indicated to be incorporated by reference.

1. (canceled)
 2. A system for automatically generating credit scoresimulation information associated with users, the system comprising: oneor more hardware processors configured to: access, from a database,credit data associated with a user, wherein the credit data includes acredit score for the user; generate a user interface for displayincluding a first user interface control for receiving an indication ofa target credit score for the user; receive the indication of the targetcredit score from the user via the first user interface control;generate an initial credit score simulation scenario associated withrespective initial credit score simulation parameters for the targetcredit score based on the credit data; generate an updated userinterface including the first user interface control and at least one ofthe initial credit score simulation parameters; receive an indication ofan updated target credit score from the user interface via the firstuser interface control; and generate an updated credit score simulationscenario with respective updated credit score simulation parametersbased on the updated target credit score.
 3. The system of claim 2,wherein the one or more hardware processors are further configured to:hide display of the initial credit score simulation parameters; anddisplay an expanded view of the updated credit score simulation scenarioadjacent to the first user interface control.
 4. The system of claim 2,wherein the first user interface control comprises a sliding bar, andwherein the indication of the updated target credit score from the useris received based at least in part on user interaction with the slidingbar.
 5. The system of claim 2, wherein the user interface furthercomprises a second user interface control for a target time frame forthe target credit score, and wherein the one or more hardware processorsare further configured to receive an indication of an updated targettime frame from the user interface, wherein to generate the updatedcredit score simulation scenario is further based on the updated targettime frame.
 6. The system of claim 5, wherein the second user interfacecontrol comprises a sliding bar, and wherein the indication of theupdated target time frame from the user is received based at least inpart on user interaction with the sliding bar.
 7. The system of claim 2,wherein the database is local to the system.
 8. The system of claim 2,wherein the database is external to the system.
 9. The system of claim2, wherein the initial credit score simulation parameters comprise atleast one of: paying off at least a certain portion of outstandingdebts, making payments on time over a certain period of time, changingan average age of accounts, changing an amount of available credit,applying for a new loan, or applying for a new credit card.
 10. Acomputer-implemented method for automatically generating credit scoresimulation information associated with users, the method comprising:accessing, from a database, credit data associated with a user, whereinthe credit data includes a credit score for the user; generating a userinterface for display including a first user interface control forreceiving an indication of a target credit score for the user; receivingthe indication of the target credit score from the user via the firstuser interface control; generating an initial credit score simulationscenario associated with respective initial credit score simulationparameters for the target credit score based on the credit data;generating an updated user interface including the first user interfacecontrol and at least one of the initial credit score simulationparameters; receiving an indication of an updated target credit scorefrom the user interface via the first user interface control; andgenerating an updated credit score simulation scenario with respectiveupdated credit score simulation parameters based on the updated targetcredit score.
 11. The computer-implemented method of claim 10 furthercomprising: hiding display of the initial credit score simulationparameters; and displaying an expanded view of the updated credit scoresimulation scenario adjacent to the first user interface control,wherein the expanded view comprises descriptive text for the at leastone initial credit score simulation parameter.
 12. Thecomputer-implemented method of claim 10, wherein the at least oneinitial credit score simulation parameter in the updated user interfaceis displayed in a color that reflects a credit risk associated with theparameter.
 13. The computer-implemented method of claim 10, whereinfirst user interface control comprises a rotary dial.
 14. Thecomputer-implemented method of claim 10, wherein the user interfacefurther comprises an indication of a positive or negative effect on acredit score corresponding to the initial credit score simulationparameters.
 15. The computer-implemented method of claim 10, wherein theuser interface further comprises an indication of an expected creditscore change over time in response to a user performing actionsrecommended in association with the at least one initial credit scoresimulation parameter.
 16. A non-transitory computer storage mediumstoring computer-executable instructions that, when executed by one ormore processors, causes the one or more processors to at least: access,from a database, credit data associated with a user, wherein the creditdata includes a credit score for the user; generate a user interface fordisplay including a first user interface control for receiving anindication of a target credit score for the user; receive the indicationof the target credit score from the user via the first user interfacecontrol; generate an initial credit score simulation scenario associatedwith respective initial credit score simulation parameters for thetarget credit score based on the credit data; generate an updated userinterface including the first user interface control and at least one ofthe initial credit score simulation parameters; receive an indication ofan updated target credit score from the user interface via the firstuser interface control; and generate an updated credit score simulationscenario with respective updated credit score simulation parametersbased on the updated target credit score.
 17. The non-transitorycomputer storage medium of claim 16, wherein the generated userinterface data includes a plurality of graphical indications in spatialrelationship for each of the initial credit score simulation parameters,wherein the graphical indications indicate positive, neutral, ornegative effect on credit scores.
 18. The non-transitory computerstorage medium of claim 16, wherein the computer-executable instructionsfurther cause the one or more processors to at least: hide display ofthe initial credit score simulation parameters; and display an expandedview of the updated credit score simulation scenario, wherein theexpanded view of the updated credit score simulation scenario includes(a) a first time frame in spatial relation with a first simulated creditscore and (b) a second time frame in spatial relation with a secondsimulated credit score, wherein the second time frame is longer than thefirst time frame.
 19. The non-transitory computer storage medium ofclaim 18, wherein the expanded view of the updated credit scoresimulation scenario includes one or more user input controls to receiveone or more score simulation parameters associated with thecorresponding updated credit score simulation parameter.
 20. Thenon-transitory computer storage medium of claim 18, wherein to displaythe expanded view of the updated credit score simulation scenarioincludes: determining that data corresponding to the expanded view ofthe updated credit score simulation scenario is cached on a usercomputing device; and updating the user interface to include theexpanded view to be positioned in spatial relation with the first userinterface control.
 21. The non-transitory computer storage medium ofclaim 18, wherein the expanded view is positioned adjacent to the firstuser interface control.